Searched hist:fbb4c094 (Results 1 – 7 of 7) sorted by relevance
| /xv6-public/ |
| H A D | exec.c | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|
| H A D | sysfile.c | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|
| H A D | vm.c | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|
| H A D | syscall.c | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|
| H A D | proc.h | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|
| H A D | defs.h | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|
| H A D | proc.c | fbb4c094 Wed Feb 01 01:21:14 GMT 2017 Frans Kaashoek <kaashoek@mit.edu> Read curproc from cpu structure, but be careful because after a schedule event
myproc() points to a different thread.
myproc();
sched();
myproc(); // this proc maybe different than the one before sched
Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.
|